LOYALTY RELEASE 26.5.0

 

Offers: Re-clip After the Usage Period Expires

Available to all CLIENTS

Background

Members can clip an Offer again after a previously clipped instance reaches the end of its usage period, as long as the Offer remains active.

Solution

When a Member attempts to clip an Offer they previously clipped, Loyalty now checks whether the prior clip usage period has expired. If it has, the system returns "success" and creates a new clip. If the prior clip is completed or cancelled, re-clipping behavior stays the same.

Key Capabilities:

• Allows re-clipping when the prior clip usage period has expired, and the Offer remains active.

• Returns a success response and creates a new clip instance for the Member.

• Keeps existing behavior unchanged for completed and cancelled Offers.

What it looks like in Loyalty

This update keeps eligible Members moving forward when they miss an earlier usage window, without changing the rules for Offers they already completed or cancelled. You can support repeat participation where it makes sense, while preserving a predictable Member experience.

Benefits:

• Lower friction: Give Members another path to participate when they miss an earlier window.

• Consistent experience: Apply a clear, repeatable rule across Offer clipping at scale.

• Operational confidence: Improve engagement outcomes without reworking existing completed or cancelled Offer logic.

 

Offers: Improved Bulk Distribution Performance

Available to all CLIENTS

Background

We improved bulk distribution performance in Issue Offers so large Batch Offer Assignment distributions finish sooner and run more consistently across File Upload, Segments, and ML Offers methods.

Solution

Enterprise teams rely on bulk issuance to activate Offer campaigns on schedule. This improvement reduces delays and helps large distributions complete with more predictable turnaround, supporting timely member communications.

Key Capabilities:

• Improves performance for large Issue Offers distributions across File Upload, Segments, and ML Offers.

• Improves consistency for long-running, high-volume distributions.

• Preserves existing bulk issuance workflows across Offer types.

What it looks like in Loyalty

Benefits:

• Faster turnaround: Complete large distributions sooner when timing matters.

• More predictable delivery: Reduce delays during high-volume execution.

• Operational confidence: Run enterprise-scale distributions with steadier performance.

Note: The size of the import file can't exceed 25 megabytes.

For more information, see Configure Batch Offer Assignment.

 

Offers: Consistent Offer Cancellation Activities Across API and Console

Available to all CLIENTS

Background

We’ve aligned Offer Response cancellations across the Offers API and the Loyalty Console so Activity tracking stays consistent, regardless of where a cancellation happens.

Solution

When an Offer Response is cancelled through the existing Offers API endpoint, Loyalty now creates the same sl_offer_cancel Activity generated by a manual cancellation in the Console.

Key Benefits

• Consistent tracking across channels: Capture cancellations the same way whether they start in the API or the Console.

• Reliable webhook triggers: Ensure cancellation webhooks fire as expected without custom workarounds.

• Cleaner integrations: Reduce operational overhead by standardizing on a single cancellation signal.

• No workflow disruption: Keep the existing endpoint and Console behavior intact, with Activity creation added automatically.

What it looks like in Loyalty

Previously, cancellations made via API did not generate an Activity, while Console cancellations did. That gap complicated enterprise workflows that depend on Activities and webhooks for monitoring and downstream automation. This change brings consistent behavior across interfaces.

Cancelling an Offer Response via the API now generates an sl_offer_cancel Activity. The Activity format matches the existing Console-generated cancellation Activity. All existing Console cancellation functionality remains unchanged.

This update improves consistency across Loyalty, and makes cancellation tracking easier to trust and act on, without changes to current implementations.

 

Order Rules: Retrieve Order Rule Configurations Through the Program API

Available to all CLIENTS

Background

We’ve introduced a new Program API endpoint that exposes Order Rule configurations, including Base and Bonus Earn Rules, directly to web and mobile applications.

Enterprise teams often configure promotions in Loyalty, but still need to recreate that logic elsewhere to support in‑app experiences. This capability removes that duplication. Applications can now consume Order Rule configuration directly from Loyalty and use it to drive promotional UI with confidence.

Solution

Loyalty clients can now retrieve Order Rule data in a structured, paginated format using a new GET endpoint under the Program API. The endpoint returns both current and future‑effective rules, along with the metadata needed to understand which products or categories qualify for base or bonus earn.

Key Benefits

• Single source of truth for promotions: Configure earn rules once in Loyalty and reuse them across digital channels.

• Dynamic, promotion‑aware experiences: Power product‑level UI treatments, such as bonus point banners, icons, or legal disclosures, based on live and scheduled Order Rules.

• Support for future planning: Retrieve upcoming promotions ahead of launch to prepare experiences without additional coordination.

• Enterprise‑ready by design: Built on existing Program API conventions with support for authentication, pagination, filtering, sorting, and business unit scoping.

What it looks like in Loyalty

A new GET endpoint returns paginated Order Rule configurations. Each Order Rule includes:

• Base Earn Rule details.

• Full Bonus Rule definitions, including conditions, qualifying items, and earn values.

• Core configuration metadata such as status, effectivity, business unit, and time zone.

Clients can filter by Effectivity (active, future, or both) and Rule status (Published, Draft, Archived).

The endpoint is designed for periodic polling and client‑side caching.

This enhancement enables Loyalty teams to deliver consistent, promotion‑aware experiences across channels, without duplicating configuration or introducing operational complexity.

For more information, see the Loyalty Program API technical documentation.

 

Messages: More Accurate Push Notification Reporting

NOT AVAILABLE FOR Loyalty Essentials

Background

We’ve improved how Loyalty tracks push notification delivery and engagement to ensure reporting reflects real Member behavior, even when the app is not actively open.

This enhancement strengthens the accuracy of notification metrics by ensuring Member apps can reliably register delivery and interaction events across common real‑world scenarios, including background and cold‑start states.

Solution

Key Benefits

• Greater confidence in notification performance: Delivery and engagement metrics now more accurately represent what Members receive and interact with.

• Clearer insight into Member engagement: Notification dashboards align more closely with real outcomes, supporting better decisions around messaging, timing, and offers.

• Consistent behavior across platforms: Improvements apply to both iOS and Android, reducing platform‑specific gaps in reporting.

• Stronger operational trust: Teams can rely on Loyalty notification data when evaluating campaign effectiveness and Member response.

What it looks like in Loyalty

This update ensures Loyalty notifications are delivered and measured with the level of accuracy enterprise teams expect when engaging Members at scale.

 

Updated Phone Validation Support

Available to all CLIENTS

Background

We’ve updated the phone validation module in this release to align with recent changes in acceptable international phone formats with the intent to deliver more accurate and comprehensive global phone validation behavior.

 

Resolved Issues

Bug Fixes

• Resolved an issue where updating an offer’s Display Name could unintentionally overwrite a Header set in the Content Editor.

• Resolved an issue in Loyalty-hosted Sign-in and Authorization pages where the sign-in and consent buttons could appear invisible due to styling conflicts, improving guest sign-in clarity and checkout continuity.

• Resolved an issue where Batch Offer Assignment CSV uploads could fail when files were saved in UTF-8 with BOM, ensuring Members map correctly during offer issuance.

• Resolved an issue where repeated Offer Response imports could leave background connections open, which could impact long-running import performance and stability.

• Resolved an issue that could trigger elevated database row locking during Offer Response processing, supporting steadier performance for high-volume activity.

• Resolved an issue where month-end, multi-metric expiration rules could skip creating an expected expiration record, ensuring points expire accurately and consistently.

• Resolved an issue where Post‑Challenge Surveys in “View YouTube” Challenges (and other “View” Challenge types) didn’t allow Admins to set a correct response.

See Loyalty Upcoming Releases for the platform release schedule.

See System Maintenance for details on the next system maintenance window, per region.

The status page provides you with regular updates regarding the status of the Loyaltyplatform in the event of a major system incident in your region. In this article we’ll explain the information you will see and how to subscribe to the Loyalty notification system to receive regular updates on the platform status, which we highly recommend to all users.

See Platform Status for more details.